Windows 7 Enterprise x64 SP1 is the ONLY update that is giving me issues. I've tried both the Windows Update method and the download and run method. The downloaded file gives the error: ERROR_SXS_COMPONENT_STORE_CORRUPT (0x80073712) I've gone through all the recommended troubleshooting steps that I can find regarding this error with the exception of reinstalling/repairing Windows. The Windows Update troubleshooter comes back clean. The SUR Tool gives the following in the log file: ================================= Checking System Update Readiness. Binary Version 6.1.7601.21645 Package Version 11.0 2011-02-24 13:13 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\x86_microsoft-windows-ie-feedsbs_31bf3856ad364e35_8.0.7600.20579_none_1776fc29cc29780f.manifest x86_microsoft-windows-ie-feedsbs_31bf3856ad364e35_8.0.7600.20579_none_1776fc29cc29780f (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7600.20579_none_94df6592004f2297.manifest wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7600.20579_none_94df6592004f2297 (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-ie-feedsbs_31bf3856ad364e35_8.0.7600.16466_none_7313c9f06b63e185.manifest amd64_microsoft-windows-ie-feedsbs_31bf3856ad364e35_8.0.7600.16466_none_7313c9f06b63e185 (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\x86_microsoft-windows-ie-feedsbs_31bf3856ad364e35_8.0.7600.16466_none_16f52e6cb306704f.manifest x86_microsoft-windows-ie-feedsbs_31bf3856ad364e35_8.0.7600.16466_none_16f52e6cb306704f Summary: Seconds executed: 937 Found 4 errors CSI Manifest Failed Catalog Check Total count: 4 Unavailable repair files: winsxs\manifests\x86_microsoft-windows-ie-feedsbs_31bf3856ad364e35_8.0.7600.20579_none_1776fc29cc29780f.manifest winsxs\manifests\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7600.20579_none_94df6592004f2297.manifest winsxs\manifests\amd64_microsoft-windows-ie-feedsbs_31bf3856ad364e35_8.0.7600.16466_none_7313c9f06b63e185.manifest winsxs\manifests\x86_microsoft-windows-ie-feedsbs_31bf3856ad364e35_8.0.7600.16466_none_16f52e6cb306704f.manifest ==================== I really have no idea what else to do. I've run sfc.exe /scannow and that repaired a number of files. I don't want to reinstall or repair install windows for 4 .manifest files that really don't seem all that relevant to my day-to-day usage. Can I just grab those manifest files from another similar Windows 7 machine? Or are they compiled/created specifically for my machine? I'm pulling my hair out here... Any thoughts on other possible solutions?

I too am having this error with Win 7 Pro. Ran the support options including the FixIt and the Checking System Update Readiness tool and it says everything is fixed, but still fails.

yes, grab them from a sendond PC. This 1 official way recommend by MS in this Guide: Advanced guidelines for diagnosing and fixing servicing corruption http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx The files are part of the Update KB976325. André"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

SP1 messed up my entire system. Had to run System Restore to gain access and use my browser to post this. 7 Pro 64-bit. The install went OK, at first, but when it came time to load my profile, all I got was 2 blank screens and a little box in the upper left of monitor 1 saying that it was configuring personalized settings for Windows Desktop Update. That was ALL it did, until I got fed up after 45 minutes and did a hard reboot. Then, I couldn't access my core profile at all. If not for System restore, I'd be spending the next 72 hours rebuilding my system from scratch.

I had this error yesterday on Windows 7 Ultimate x64 system. I was able to repair my computer and install SP1 ... eventually. First, I tried the "System Update Readiness Tool". This appeared on Windows Update once I had a failed installation of SP1. On Windows Update, I had to "Check for updates" and then this tool showed up. I ran it (twice) ... but it didn't work successfully on my system. Next I tried a System Restore and then tried to install SP1 again. It failed. Unfortunately, "Windows Update error 80073712" indicates that the Windows component store is corrupt. (The component store holds the files and information that's used to install updates.) This error instructs you to restart your computer, insert the Windows installation DVD, on the DVD run setup.exe, "install now", click on "Go online to obtain the latest updates for installation", Upgrade. On my computer, it reinstalled Windows, kept most of my settings and took 3 hours and multiple reboots. Once that's done Windows Update had about 63 mandatory updates - I ran them all successfully (35 minutes). After the automatic reboot, Windows Update showed SP1 was again available for installation - I ran it successfully (just over 1 hour). 4 hours 30 minutes once I started the instructions on the error page. How did this happen to me? Once you start SP1 you cannot interrupt it. The screen said it is downloading so I thought I could halt it safely and start over when I had more time. Big mistake! When it's downloading, I think it is actually in the installation process (based on heavy CPU usage). That's how I corrupted this thing called the Windows component store. I hope my experience helps you. Good luck.

Gene, yes, I would agree. I NEVER interrupt a service pack. I hosed one vista machine doing that. Ichigo (nice - Bleach fan I take it), unfortunately, I've heard plenty of horror stories about service packs doing that sort of thing. You would think that by now MS would be able to minimize the impact of bad service pack installs. The reason I'm so persistent on this isn't that I really want the service pack, but I want to know how to fix these issues when they occur, and it's better to mess up my computer than a customer's computer. Andre, I'm gonna read over that article and give that a try. I'll let you all know what I find.Jonathan Gaskell MCSA (2003), MCITP: Server Administrator

That did it Andre. I grabbed the matching manifest files from a co-worker's PC, and placed them in the folder specified in the article. Re-ran the System Update Readiness tool, which completed successfully and repaired the files on my system using the files from my co-worker's system. I re-ran the SP1 installer that I had downloaded, and it completed successfully. It took over an hour to install, but once it installed, my system came back and functions properly. Thanks!Jonathan Gaskell MCSA (2003), MCITP: Server Administrator

nice to hear that it worked."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Hello Gentlemen, I installed SP-1 successfully on my laptop running W7 X64 Home Premium without a hitch. My desktop is another matter. After getting repeated errors during the "Windows Update" process, I downloaded the ISO (1.90 GB) and tried to install it from the DVD. I still get the "Error: ERROR_SXS_COMPONENT_STORE_CORRUPT(0x80073712)" error. I then installed "System Update Readiness Tool" Below is from Windows Update after the install... ********************************************************** System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2011] Installation date: ‎2/‎26/‎2011 12:04 PM Installation status: Successful Update type: Important This tool is being offered because an inconsistency was found in the Windows servicing store which may prevent the successful installation of future updates, service packs, and software. This tool checks your computer for such inconsistencies and tries to resolve issues if found. *********************************************************** I then rebooted, and tried again to install SP-1 and still get the same error. Below is the text from the "CheckSUR" file. *********************************************************** Checking System Update Readiness. Binary Version 6.1.7601.21645 Package Version 11.0 2011-02-26 17:52 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store Summary: Seconds executed: 92 No errors detected *********************************************************** I wish I would have found errors, at least I would have a shot at repairing them. Thanks, Bob

Bob, I'd recommend starting a new thread to get more attention on your issue. This thread has already been marked solved. You may want to try to run the System File Checker (open cmd.exe, and run sfc.exe /scannow). You may also want to run a check disk to make sure you aren't having any other errors on your hard drive. It's strange that you're getting a component store corrupt error, but no errors are found in the SUR tool logs. Unfortunately, I was pretty dumbfounded with this error too, so I don't have any other suggestions.Jonathan Gaskell - MCSA (2003), MCITP: Server Administrator

yes, grab them from a sendond PC. This 1 official way recommend by MS in this Guide: Advanced guidelines for diagnosing and fixing servicing corruption http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx The files are part of the Update KB976325. André "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ Sorry for rearing an ancient thread, but wanted to say thanks. I also have an important addition to the above/below linked instructions. It's a shame this solution isn't easier to Google and find. http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx Also add, that people should run "ChkDsk C: /R" from an elevated command prompt, and restart, prior to going forward with any additional steps. What led to the problem on this particular PC, was ONE corrupt file under "C:\Windows\WinSxS\Manifests". There were a few corrupt sectors on the harddrive and these files are neither flagged by SigVerif.Exe, or SFC.Exe. Prior to replacing the corrupt file, (that was identified as "unsigned" by SysInternals SigCheck.Exe by the way,) all updates would go through successfully except SP1 and IE9. I've attempted to service many systems from XP to Vista to W7 with a corrupt Side-by-Side store, but this is the first one where I didn't have to start over with a fresh install. I had in the past on other systems, even tried surgical removal and replacement on the relevant registry keys and filesystem data store, to no avail. In this case, and since I had another system at the same SP0 level, I was able to simply modify permissions, replace the affected file identified by the from "C:\Windows\logs\cbs\checksur.log" check for "HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\@CorruptWinners" as instructed, then rerun the updates. Voila!